- connect many, legacy databases - all of which operate separately and in silos
- hire contractors rather than listening to in house experts
- set the "product" launch as a fixed deadline that cannot be missed, regardless of site status
- do some testing - but there'll be no time to really pay attention to the results
- throw more people at fixing the "technical" problem(s), that's the ticket to success
- use Google Analytics to measure traffic and usage - it doesn't cost anything* (found the beacon, just need confirmation that they didn't buy the premium version)
- blame the site sponsor for throwing in last minute requirements
Outrage is a good thing. It means you still care. For my daily outrage, stop by when you can.
Thursday, October 24, 2013
Act 1, Scene 1...
Can't WAIT for the faux outrage at today's hearings. So here's what we "know" about the ACA website requirements:
Subscribe to:
Post Comments (Atom)
2 comments:
Amen to that sister!! Add to the facts that managers never think about the web as the primary communication tool but want to cut cost as much as possible. And also add to the list . . . they don't listen when their being told that there are problems because that's not what they want to hear.
Ellen, are you on Facebook? If so, look me up: Stephanie Stella Wojczynski
Post a Comment